Call-Stack Coverage for GUI Test Suite Reduction

Test-Suite Reduction and Prioritization for Modified Condition/Decision Coverage

Software testing is particularly expensive for developers of high-assurance software, such as software that is produced for commercial airborne systems. One reason for this expense is the Federal Aviation Administration’s requirement that test suites be modified condition/decision coverage (MC/DC) adequate. Despite its cost, there is evidence that MC/DC is an effective verification technique an...

A greedy approach for coverage-based test suite reduction

Software testing is an activity to find maximum number of errors which have not been discovered yet with optimum time and effort. As the software evolves the size of the test suite and grows with new test cases being added to the test suite. However, due to time and resource constraints rerunning all the test cases in the test suite is not possible, every time the software is modified, in order...

Redundancy Based Test-Suite Reduction

The size of a test-suite has a direct impact on the costs and the effort of software testing. Especially during regression testing, when software is re-tested after some modifications, the size of the testsuite is important. Common test-suite reduction techniques select subsets of test-suites that achieve given test requirements. Unfortunately, not only the test-suite size but also the fault de...

Coverage-driven Automated Compiler Test Suite Generation

Event-Coverage and Weight based Method for Test Suite Prioritization

There are many challenges in testing of Graphical User Interface (GUI) applications due to its event driven nature and infinite input domain. Testing each and every possible combination of input require creating number of test cases to satisfy the adequacy criteria of GUI testing. It is not possible to test each and every test case within specified time frame. Therefore it is important to assig...